Methods and devices for injecting commands in systems having multiple multi-processor clusters

ABSTRACT

Techniques and devices are provided for injecting transactions within computer systems having a plurality of multi-processor clusters. Each cluster includes a plurality of nodes, including processors, a service processor and an interconnection controller interconnected by point-to-point intra-cluster links. The processors and the interconnection controller in each cluster make transactions via an intra-cluster transaction protocol. Inter-cluster links are formed between interconnection controllers of different clusters. Each of the processors and the interconnection controller in a cluster has a test interface for communicating with the service processor. The service processor is configured to make an injected transaction according to the intra-cluster transaction protocol via one of the test interfaces. In preferred embodiments, the service processor is configured to make an injected transaction according to the intra-cluster transaction protocol via a test interface of an interconnection controller in the same cluster.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application Ser. No.09/932,456, filed Aug. 16, 2001 and U.S. patent application Ser. Nos.10/157,384 and 10/156,893, both of which were filed on May 28, 2002. Allof the foregoing applications are hereby incorporated by reference.

BACKGROUND OF THE INVENTION

The present invention relates generally to multi-processor computersystems. More specifically, the present invention provides techniquesfor building computer systems having a plurality of multi-processorclusters.

A relatively new approach to the design of multi-processor systemsreplaces broadcast communication among processors with a point-to-pointdata transfer mechanism in which the processors communicate similarly tonetwork nodes in a tightly-coupled computing system. That is, theprocessors are interconnected via a plurality of communication links andrequests are transferred among the processors over the links accordingto routing tables associated with each processor. The intent is toincrease the amount of information transmitted within a multi-processorplatform per unit time.

Previous implementations of such systems have had shortcomings. Some ofthese shortcomings relate to obtaining debugging information while thesystem is running. For example, prior implementations do not provide theability to determine a configuration state of nodes in a cluster whilethe system is running. Instead, the system would need to be brought downin order to determine such configurations. Similarly, priorimplementations have had a limited ability to respond to informationdetermined during a debugging operation. For example, it would bedesirable to fix problems such as deadlocks due to dropped packets,etc., without bringing the system down. It is therefore desirable toprovide methods and devices by which multiple-cluster computing systemshave improved troubleshooting and debugging functionality.

SUMMARY OF THE INVENTION

According to the present invention, techniques are provided forinjecting transactions within computer systems having a plurality ofmulti-processor clusters. Each cluster includes a plurality of nodes,including processors, a service processor and an interconnectioncontroller interconnected by point-to-point intra-cluster links. Theprocessors and the interconnection controller in each cluster maketransactions via an intra-cluster transaction protocol. Inter-clusterlinks are formed between interconnection controllers of differentclusters.

Each of the processors and the interconnection controller in a clusterhas a test interface for communicating with the service processor. Theservice processor is configured to make an injected transactionaccording to the intra-cluster transaction protocol via one of the testinterfaces. In preferred embodiments, the service processor isconfigured to make an injected transaction according to theintra-cluster transaction protocol via a test interface of aninterconnection controller in the same cluster.

Some embodiments of the invention provide a computer system. Thecomputer system includes a plurality of processor clusters, each clusterincluding a plurality of nodes. The nodes include processors and aninterconnection controller interconnected by point-to-pointintra-cluster links. Each of the processors and the interconnectioncontroller communicate within a cluster via an intra-cluster transactionprotocol. Inter-cluster links are formed between interconnectioncontrollers of different clusters. The interconnection controllers maycommunicate between clusters via an inter-cluster transaction protocol.Each of the processors and the interconnection controller in a clusterhas a test interface for communicating with a service processor.

At least one of the nodes in a cluster is a command-injecting nodeconfigured to receive a command via a test interface and to inject thecommand into a queue of commands according to the intra-clustertransaction protocol. The test interface may be compliant with the JointTest Action Group standard. The test interface may also include (or atleast may be in communication with) a mailbox register for receiving thecommand. The mailbox register may be connected with a test data ininterface and a test data out interface. The command may be receivedfrom the test interface in a first clock domain and at least part of thecommand-injecting node may operate in a second clock domain.

The injected command may be selected from the group consisting of (a) acommand for reading a configuration of a node within a local clusterthat includes the service processor that made the injected transaction;(b) a command for writing a configuration of a node within a localcluster that includes the service processor that made the injectedtransaction; (c) a command for reading a configuration of a node withina remote cluster that does not include the service processor that madethe injected transaction; and (d) a command for writing a configurationof a node within a remote cluster that does not include the serviceprocessor that made the injected transaction.

The injected command may be, for example, a new transaction or a part ofa transaction that was in progress before the command was injected. Thenew transaction may be within a local cluster that includes thecommand-injecting node or within a remote cluster that includes thecommand-injecting node.

The command-injecting node may be any device capable of driving the JTAGport, e.g., an interconnection controller. The command-injecting nodemay be further configured for receiving injected transactions in thefirst clock domain and synchronizing the injected transactions to thesecond clock domain.

Alternative embodiments of the invention provide an interconnectioncontroller for use in a computer system comprising a plurality ofprocessor clusters, wherein each cluster includes a plurality of nodes(including processors) and an instance of the interconnection controllerinterconnected by point-to-point intra-cluster links. Each of theprocessors and the interconnection controller within a clustercommunicate via an intra-cluster transaction protocol. Theinterconnection controller is configured to receive commands via a testinterface and to inject the commands into a queue of pending commandsaccording to the intra-cluster transaction protocol.

A service processor in a cluster that includes the interconnectioncontroller may operate in a first clock domain and the interconnectioncontroller may operate in a second clock domain. The interconnectioncontroller may be further configured for receiving injected transactionsfrom the service processor in the first clock domain and synchronizingthe injected transactions to the second clock domain.

The interconnection controller may include a mailbox register forreceiving the injected transaction from the service processor. At leastone computer-readable medium having data structures stored therein maybe representative of the interconnection controller. The data structuresmay include a simulatable representation of the interconnectioncontroller. The simulatable representation may include a netlist. Thedata structures may include a code description of the interconnectioncontroller. The code description may correspond to a hardwaredescription language.

The interconnection controller may be embodied in an integrated circuit.The integrated circuit may be an application-specific integratedcircuit. A set of semiconductor processing masks may be representativeof at least a portion of the interconnection controller.

A protocol engine may control the queue of pending commands. Theinterconnection controller may be further configured to process accesscommands for accessing configuration registers of the interconnectioncontroller without forwarding the access commands to the protocolengine. The interconnection controller may include a configurationaccess unit for processing access commands.

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the remaining portions of thespecification and the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are diagrammatic representations depicting systemshaving multiple clusters.

FIG. 2 is a diagrammatic representation of an exemplary cluster having aplurality of processors for use with specific embodiments of the presentinvention.

FIG. 3A is a diagrammatic representation of an exemplary interconnectioncontroller for facilitating various embodiments of the presentinvention.

FIG. 3B is a diagrammatic representation of an exemplary test interfaceof an interconnection controller for facilitating various embodiments ofthe present invention.

FIG. 3C is a state diagram of a test access port according to the JointTest Action Group standard.

FIG. 4A is a diagrammatic representation of a service processor for usewith various embodiments of the present invention.

FIG. 4B is a diagrammatic representation of a local processor for usewith various embodiments of the present invention.

FIG. 5 is a diagrammatic representation of a memory mapping schemeaccording to a particular embodiment of the invention.

FIG. 6A is a simplified block diagram of a four cluster system forillustrating a specific embodiment of the invention.

FIG. 6B is a combined routing table including routing information forthe four cluster system of FIG. 6A.

FIG. 7 is a flow chart that provides an overview of a command injectionprocess according to some implementations of the invention.

FIG. 8 depicts the format of a mailbox register according to someimplementations of the invention.

FIG. 9 illustrates a mailbox register in a test clock domain and acorresponding mailbox register in a clock domain of an interconnectioncontroller.

FIG. 10 is a block diagram that illustrates components of aninterconnection controller that can implement some features of thepresent invention.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

Reference will now be made in detail to some specific embodiments of theinvention including the best modes contemplated by the inventors forcarrying out the invention. Examples of these specific embodiments areillustrated in the accompanying drawings. While the invention isdescribed in conjunction with these specific embodiments, it will beunderstood that it is not intended to limit the invention to thedescribed embodiments. On the contrary, it is intended to coveralternatives, modifications, and equivalents as may be included withinthe spirit and scope of the invention as defined by the appended claims.Multi-processor architectures having point-to-point communication amongtheir processors are suitable for implementing specific embodiments ofthe present invention. In the following description, numerous specificdetails are set forth in order to provide a thorough understanding ofthe present invention. The present invention may be practiced withoutsome or all of these specific details. Well known process operationshave not been described in detail in order not to unnecessarily obscurethe present invention. Furthermore, the present application's referenceto a particular singular entity includes that possibility that themethods and apparatus of the present invention can be implemented usingmore than one entity, unless the context clearly dictates otherwise.

FIG. 1A is a diagrammatic representation of one example of a multiplecluster, multiple processor system which may employ the techniques ofthe present invention. Each processing cluster 101, 103, 105, and 107includes a plurality of processors. The processing clusters 101, 103,105, and 107 are connected to each other through point-to-point links111 a-f. The multiple processors in the multiple cluster architectureshown in FIG. 1A share a global memory space. In this example, thepoint-to-point links 11 a-f are internal system connections that areused in place of a traditional front-side bus to connect the multipleprocessors in the multiple clusters 101, 103, 105, and 107. Thepoint-to-point links may support any point-to-point coherence protocol.

FIG. 1B is a diagrammatic representation of another example of amultiple cluster, multiple processor system that may employ thetechniques of the present invention. Each processing cluster 121, 123,125, and 127 is coupled to a switch 131 through point-to-point links 141a-d. It should be noted that using a switch and point-to-point linksallows implementation with fewer point-to-point links when connectingmultiple clusters in the system. A switch 131 can include a generalpurpose processor with a coherence protocol interface. According tovarious implementations, a multi-cluster system shown in FIG. 1A may beexpanded using a switch 131 as shown in FIG. 1B.

FIG. 2 is a diagrammatic representation of a multiple processor clustersuch as, for example, cluster 101 shown in FIG. 1A. Cluster 200 includesprocessors 202 a-202 d, one or more Basic I/O systems (BIOS) 204, amemory subsystem comprising memory banks 206 a-206 d, point-to-pointcommunication links 208 a-208 e, and a service processor 212. Thepoint-to-point communication links are configured to allowinterconnections between processors 202 a-202 d, I/O switch 210, andinterconnection controller 230. The service processor 212 is configuredto allow communications with processors 202 a-202 d, I/O switch 210, andinterconnection controller 230 via a JTAG interface represented in FIG.2 by links 214 a-214 f. It should be noted that other interfaces aresupported. I/O switch 210 connects the rest of the system to I/Oadapters 216 and 220, and to BIOS 204 for booting purposes.

Service processor 212 is primarily responsible for partitioning theresources of cluster 200. According to some embodiments, serviceprocessor 212 allocates usage of processor 202 a-202 d and I/O switch210 although service processor 212 could be programmed to managedirectly other resources such as, for example, memory banks or variousI/O devices. Service processor 212 may be configured, for example, via amanagement/server console (not shown) to which service processor 212 isconnected.

According to specific embodiments, service processor 212 has theintelligence to partition system resources according to previouslyspecified partitioning schema. The partitioning can be achieved throughdirect manipulation of routing tables associated with the systemprocessors by service processor 212. Such partitioning is made possibleby the point-to-point communication infrastructure. The routing tablescan also be changed by execution of the BIOS code in one or moreprocessors. The routing tables are used to control and isolate varioussystem resources, the connections between which are defined therein.

According to a specific embodiment, service processor 212 is anautonomous processor with its own set of operating system applications(which is separate from the operating system(s) associated with the restof the system) and its own I/O. Service processor 212 can run when therest of the processors, memory, and I/O are not functioning. Serviceprocessor 212 can operate as an external supervising intelligence thatensures all of the system resources are operating as desired.

It should be noted, however, that the previously-specified partitioningschema need not be implemented by a separate service processor. That is,for example, one of the system processors could be employed for thispurpose. According to such an embodiment, for example, the system BIOScould be altered to effect the schema using the system's primaryprocessor.

In addition, a partition may represent a variety of system resourcecombinations. That is, for example, in a “capacity on demand” scenario apartition could be represented by a single processor, removal of theprocessor from its partition rendering the remaining components unableto run an OS (and therefore the user would not be charged for thispartition). A partition could also be represented by a processor andsome associated memory or I/O. In general, any functional subset of theresources available in a computer system can be thought of as apartition.

The processors 202 a-d are also coupled to an interconnection controller230 through point-to-point links 232 a-d. According to variousembodiments and as will be described below in greater detail,interconnection controller 230 performs a variety of functions whichenable the number of interconnected processors in the system to exceedthe node ID space and mapping table limitations associated with each ofa plurality of processor clusters. According to some embodiments,interconnection controller 230 performs a variety of other functionsincluding the maintaining of cache coherency across clusters.Interconnection controller 230 can be coupled to similar controllersassociated with other multi-processor clusters. It should be noted thatthere can be more than one such interconnection controller in onecluster. Interconnection controller 230 communicates with bothprocessors 202 a-d as well as remote clusters using a point-to-pointprotocol.

More generally, it should be understood that the specific architectureshown in FIG. 2 is merely exemplary and that embodiments of the presentinvention are contemplated having different configurations and resourceinterconnections, and a variety of alternatives for each of the systemresources shown. However, for purpose of illustration, specific detailsof cluster 200 will be assumed. For example, most of the resources shownin FIG. 2 are assumed to reside on a single electronic assembly. Inaddition, memory banks 206 a-206 d may comprise double data rate (DDR)memory which is physically provided as dual in-line memory modules(DIMMs). I/O adapter 216 may be, for example, an ultra direct memoryaccess (UDMA) controller or a small computer system interface (SCSI)controller which provides access to a permanent storage device. I/Oadapter 220 may be an Ethernet card adapted to provide communicationswith a network such as, for example, a local area network (LAN) or theInternet. BIOS 204 may be any persistent memory like flash memory.

According to one embodiment, service processor 212 is a Motorola MPC855Tmicroprocessor which includes integrated chipset functions, andinterconnection controller 230 is an Application Specific IntegratedCircuit (ASIC) supporting the local point-to-point coherence protocol.Interconnection controller 230 can also be configured to handle anon-coherent protocol to allow communication with I/O devices. In oneembodiment, interconnection controller 230 is a specially configuredprogrammable chip such as a programmable logic device or a fieldprogrammable gate array. In another embodiment, the interconnectcontroller 230 is an Application Specific Integrated Circuit (ASIC). Inyet another embodiment, the interconnect controller 230 is a generalpurpose processor augmented with an ability to access and processinterconnect packet traffic.

FIG. 3 is a diagrammatic representation of one example of aninterconnection controller 230 for facilitating various aspects of thepresent invention. According to various embodiments, the interconnectioncontroller includes one or more protocol engines 305 configured tohandle packets such as probes and requests received from variousclusters of a multi-processor system. The functionality of the protocolengine 305 can be partitioned across several engines to improveperformance. In one example, partitioning is done based on packet type(request, probe and response), direction (incoming and outgoing), ortransaction flow (request flows, probe flows, etc).

The protocol engine 305 has access to a pending buffer 309 that allowsthe interconnection controller to track transactions such as recentrequests and probes and associate the transactions with specific nodes,e.g., from specific processors. Transaction information maintained inthe pending buffer 309 can include transaction destination nodes, theaddresses of requests for subsequent collision detection and protocoloptimizations, response information, tags, and state information. Aswill become clear, this functionality is leveraged to enable particularaspects of the present invention.

The interconnection controller has a coherent protocol interface 307that allows the interconnection controller to communicate with otherprocessors in the cluster as well as external processor clusters. Theinterconnection controller may also include other interfaces such as anon-coherent protocol interface 311 for communicating with I/O devices(e.g., as represented in FIG. 2 by links 208 c and 208 d). According tovarious embodiments, each interface 307 and 311 is implemented either asa full crossbar or as separate receive and transmit units usingcomponents such as multiplexers and buffers. It should be noted that theinterconnection controller 230 does not necessarily need to provide bothcoherent and non-coherent interfaces. It should also be noted that aninterconnection controller 230 in one cluster can communicate with aninterconnection controller 230 in another cluster.

Interconnection controller 230 also includes test interface 313 forcommunicating with service processor 212. In the specific embodimentillustrated in FIG. 3B, test interface 313 is compliant with the JointTest Action Group (JTAG) standard, i.e., IEEE Standard Test Access Portand Boundary Scan Architecture, IEEE 1149.1-2001, the entire disclosureof which is incorporated herein by reference for all purposes. The JTAGstandard describes, inter alia, the requirements for a test access port(TAP) and boundary scan architecture. However, other test interfaces maybe used to implement the present invention.

As is well known, test interface 313 may be a serial interface thatconnects a series of data registers in test data block 315 between aserial input (here, test data in (TDI) 317) and serial output (here,test data out (TDO) 319) pins. The selection of which register is to beconnected between TDI 317 and TDO 319 is controlled by a TAP controller321 and an instruction register 323. That is, TAP controller 321 selectsinstruction register 323 and a new instruction is shifted intoinstruction register 323 via the TDI input 317. This instruction selectsfor a particular one of the data registers in test data block 315 to beplaced into the serial data stream for any of a variety of operationsincluding, for example, the loading of test data into the data registerfrom the TDI input 317, the loading of test results into the dataregister from the circuit or system being tested, and the shifting ofthe test results out of the data register onto the TDO output 319.

As stated above, test data block 315 includes a plurality of dataregisters. Some of these registers may correspond to conventional JTAGdata registers. For example, the data registers could correspond to, forexample, a bypass register, a boundary scan register or a deviceidentification register. According to various specific embodiments ofthe invention, test data block 315 also includes at least one registerthat allows transactions to be injected into a fabric of transactions.

As used herein, a protocol for transactions sent on an intra-clusterlink will sometimes be referred to as an “intra-cluster protocol” and aprotocol for transactions sent on an inter-cluster link will sometimesbe referred to as an “inter-cluster protocol.” Specific embodiments ofmultiple-cluster architecture have used the same protocol fortransactions sent on both intra-cluster and inter-cluster links. Onesuch protocol is HyperTransport™ (HT) protocol, which was specificallydesigned for communication of commands and data among subsystems of acomputer system, such as multiple levels of processor caches, local andremote memory elements and various input/output (I/O) devices. The whitepaper entitled “Meeting the I/O Bandwidth Challenge: How HyperTransportTechnology Accelerates Performance in Key Applications” (HyperTransport™Consortium, December 2002) is hereby incorporated by reference.

According to some implementations of the invention, an interconnectioncontroller mailbox register that provides a mechanism by which commands,data and/or transactions may be injected according to, for example, anintra-cluster protocol used for transactions between an interconnectioncontroller and other nodes in a cluster. If such transactions involvecommunication with other clusters, the transactions may be converted toan inter-cluster protocol for communication between interconnectioncontrollers in different clusters. One example of such an inter-clusterprotocol is described in U.S. Patent Application No. ______, attorneydocket no. NWISP039, which is hereby incorporated by reference for allpurposes. The inter-cluster protocol may be the same as, substantiallythe same as, or substantially different from the intra-cluster protocol.

According to specific implementations of the invention, theintra-cluster protocol is the HyperTransport™ (HT) protocol and themailbox register allows commands and/or data to be injected into a queueof HT transactions by service processor 212. Although the HT protocol isoften used as an example of an intra-cluster and/or an inter-clusterprotocol in this disclosure, the present invention can be used with anyof a wide variety of suitable protocol(s). In alternative embodiments, amailbox register in another node, e.g., in one of processors 202, allowssuch commands and/or data to be injected.

TAP controller 321 typically implements a finite state machine (FSM),the state of which is controlled by a plurality of inputs. According toa more specific embodiment, the operation of the TAP controller FSM isrepresented by the state diagram in FIG. 3C, which is a state diagramaccording to the JTAG standard. The test access port is controlled bythe test clock (TCK) and test mode select (TMS) inputs indicated in FIG.3B, which determine whether an instruction register (IR) scan or a dataregister (DR) scan is performed. According to some implementations ofthe invention, a DR corresponds to a mailbox register used to injecttransactions and an IR is used to apply instructions to TAP controller321.

According to the JTAG standard, TAP controller 321 is driven by bothclock edges of the TCK input and responds to TMS input as shown in FIG.3C. TMS and TDI are sampled on the rising edge of the TCK signal and TDOchanges at the falling edge of the TCK signal. The values indicated nextto each state transition in FIG. 3C represent the signal present at theTMS at the rising edge of the TCK signal.

The principal part of the TAP controller FSM consists of six steadystates: Test-Logic-Reset state 330, Run-Test/Idle state 332, Shift-DRstate 334, Pause-DR state 336, Shift-IR state 338 and Pause-IR state340. According to the JTAG protocol, only one steady state(Test-Logic-Reset 330) exists for the condition in which TMS is sethigh. Therefore, the test logic can be reset within 5 TCK signals orless by setting the TMS input high.

During normal operation (or at power up), the TAP controller is forcedinto the Test-Logic-Reset state 330 by driving the TMS input high and byusing 5 or more TCK signals. In Test-Logic-Reset state 330, TAPcontroller 321 issues a reset signal, causing all test logic to be in acondition that does not hinder normal operation. When test access isneeded, a protocol is indicated by the TCK and TMS inputs that causesTAP controller 321 to exit Test-Logic-Reset state 330 and proceedthrough the appropriate states. From Run-Test/Idle state 332, aninstruction register scan (or a data register scan) can be issued tomove TAP controller 321 through the appropriate states. As shown in FIG.3C, each state of an instruction register scan has a corresponding statefor a data register scan.

The first action of either scan operation is a capture operation. For adata register scan, TAP controller 321 enters Capture DR state 342 andfor an instruction register scan, TAP controller 321 enters Capture IRstate 344. In Capture DR state 342, data are loaded into the selectedserial data path. In Capture IR state 344, status information iscaptured by the instruction register.

From a Capture state, TAP controller 321 enters either a Shift state oran Exit1 state. More commonly, TAP controller 321 enters a Shift state,enabling test data or status information to be shifted out forinspection and new data/information to be shifted in. After a Shiftstate, TAP controller 321 transitions either to Run-Test/Idle state 332by way of the Exit1 and Update states, or to a Pause state via Exit1.The Pause state may be entered in order to temporarily stop shiftingdata through the selected instruction or data register while a necessaryoperation is performed (e.g., refilling a test memory buffer). Shiftingdata through the register may resume after a Pause state by returning toa Shift state by way of an Exit2 state. Alternatively, shifting datathrough the register may be stopped by transitioning to Run-Test/Idlestate 332 by way of the Exit2 and Update states.

FIG. 4A is a high-level block diagram of the interconnections forservice processor 212 according to one implementation. In this example,service processor 212 has various functions, including partitioning ofsystem resources, controlling test interface 412 and other functions. Itis important to note that a partitioning engine could look verydifferent from service processor 212 as depicted in FIG. 4A. That is,any mechanism that can intelligently reconfigure the routing tablesusing a point-to-point communication infrastructure could perform suchpartitioning. For example, other possible mechanisms include using oneor more of processors 202 to effect the partitioning.

In this embodiment, service processor 212 has direct connections to aDRAM storage block 402 and flash memory 404. DRAM 402 facilitatesexecution by the service processor of a program stored in flash 404.Service processor 212 is also connected via PCI bus 406 to a sensorinterface 408, an Ethernet card 410, and a JTAG interface 412. Sensorinterface 408 may include, for example, inputs from monitoring circuits(not shown) which provide indications of temperature, supply voltage, orsecurity locks. Sensor interface 408 may also have various outputs suchas, for example, a control signal for activating the system's fan.Ethernet card 410 provides an interface between service processor 212and, for example, a service console by which the network administratorcan monitor and configure the server.

In the specific embodiment described herein, test interface 412 (liketest interface 313) is compliant with the JTAG standard. Test interface412 includes a TAP with several pins, including a TDI pin, a TDO pin, atest clock (TCK) pin, a test mode select (TMS) pin, and, optionally, atest reset (TRST) pin for driving the TAP controller to thetest-logic-reset state.

As will be explained further below, test interface 412 facilitatescommunication between service processor 212 and processors 202 a-202 d,thereby enabling both static and dynamic partitioning of the computersystem's resources. According to a specific embodiment, thiscommunication is facilitated using a simple outbound multiplexer.

According to various embodiments of the invention, processors 202 a-202d are substantially identical. FIG. 4B is a simplified block diagram ofsuch a processor 202, which includes an interface 422 having a pluralityof ports 414 a-414 c and routing tables 416 a-416 c associatedtherewith. Each port 414 allows communication with other resources,e.g., processors or I/O devices, in the computer system via associatedlinks, e.g., links 208 a-208 e of FIG. 2.

The infrastructure shown in FIG. 2 can be generalized as apoint-to-point, distributed routing mechanism which comprises aplurality of segments interconnecting the systems processors accordingto any of a variety of topologies, e.g., ring, mesh, etc. Each of theendpoints of each of the segments is associated with a connectedprocessor that has a unique node ID and a plurality of associatedresources that it “owns,” e.g., the memory and I/O to which it isconnected.

The routing tables associated with each of the nodes in the distributedrouting mechanism collectively represent the current state ofinterconnection among the computer system resources. Each of theresources (e.g., a specific memory range or I/O device) owned by anygiven node (e.g., processor) is represented in the routing table(s)associated with the node as an address. When a request arrives at anode, the requested address is compared to a two level entry in thenode's routing table identifying the appropriate node and link, i.e.,given a particular address within a range of addresses, go to node x;and for node x use link y.

As shown in FIG. 4B, processor 202 can conduct point-to-pointcommunication with three other processors according to the informationin the associated routing tables. According to a specific embodiment,routing tables 416 a-416 c comprise two-level tables, a first levelassociating the unique addresses of system resources (e.g., a memorybank) with a corresponding node (e.g., one of the processors), and asecond level associating each node with the link (e.g., 208 a-208 e) tobe used to reach the node from the current node.

Processor 202 also has a set of JTAG handshake registers 418 which,among other things, facilitate communication between the serviceprocessor (e.g., service processor 212 of FIG. 2) and processor 202.That is, the service processor can write routing table entries tohandshake registers 418 for eventual storage in routing tables 416 a-416c. It should be understood that the processor architecture depicted inFIG. 4B is merely exemplary for the purpose of describing a specificembodiment of the present invention. For example, a fewer or greaternumber of ports and/or routing tables may be used to implement otherembodiments of the invention.

According to a specific embodiment, cluster 200 of FIG. 2 may beconfigured using the techniques described herein to operate as a singlefour-processor system, or as two or more functionally separatepartitions. In contrast to a “greedy” algorithm, which operates withouta priori knowledge of the eventual system configuration, serviceprocessor 212 facilitates the configuration of cluster 200 by generatingand/or dynamically altering the routing tables associated with all orsome of processors 202 a-202 d (and I/O switch 210) according topreviously-specified partitioning schema. This can be accomplished byservice processor 212 writing routing table entries to the JTAGhandshake registers of the appropriate processors (and similar tablesassociated with I/O switch 210) via interface links 214 a-214 e. Asdescribed in U.S. patent application Ser. No. 09/932,456, filed Aug. 16,2001, which is incorporated by reference in its entirety, this systemconfiguring/partitioning may be done either statically, e.g., at serverboot up, or dynamically, e.g., during operation of cluster 200.

As mentioned above, the basic protocol upon which the clusters inspecific embodiments of the invention are based provides for a limitednode ID space which, according to a particular implementation, is a3-bit space, therefore allowing for the unique identification of only 8nodes. That is, if this basic protocol is employed without theinnovations represented by the present invention, only 8 nodes may beinterconnected in a single cluster via the point-to-pointinfrastructure. To get around this limitation, the present inventionintroduces a hierarchical mechanism that preserves the single-layeridentification scheme within particular clusters while enablinginterconnection with and communication between other similarly situatedclusters and processing nodes.

According to a specific embodiment, at least one of the nodes in eachmulti-processor cluster corresponds to an interconnection controller,e.g., interconnection controller 230 of FIG. 2, which manages thehierarchical mapping of information thereby enabling multiple clustersto share a single memory address space while simultaneously allowing theprocessors within its cluster to operate and to interact with anyprocessor in any cluster without “knowledge” of anything outside oftheir own cluster. The interconnection controller appears to itsassociated processor to be just another one of the processors or nodesin the cluster.

In the basic protocol, when a particular processor in a clustergenerates a request, a set of address mapping tables are employed to mapthe request to one of the other nodes in the cluster. That is, each nodein a cluster has a portion of a shared memory space with which it isassociated. There are different types of address mapping tables for mainmemory, memory-mapped I/O, different types of I/O space, etc. Theseaddress mapping tables map the address identified in the request to aparticular node in the cluster.

A set of routing tables are then employed to determine how to get fromthe requesting node to the node identified from the address mappingtable. That is, as discussed above, each processor (i.e., cluster node)has associated routing tables which identify a particular link in thepoint-to-point infrastructure which may be used to transmit the requestfrom the current node to the node identified from the address mappingtables. Although generally a node may correspond to one or a pluralityof resources (including, for example, a processor), it should be notedthat the terms node and processor are often used interchangeably herein.According to a particular implementation, a node comprises multiplesub-units, e.g., CPUs, memory controllers, I/O bridges, etc., each ofwhich has a unit ID.

In addition, because individual transactions may be segmented innon-consecutive packets, each packet includes a unique transaction tagto identify the transaction with which the packet is associated withreference to the node which initiated the transaction. According to aspecific implementation, a transaction tag identifies the source node(3-bit field), the source node unit (2-bit field), and a transaction ID(S-bit field).

Thus, when a transaction is initiated at a particular node, the addressmapping tables are employed to identify the destination node (and unit)which are then appended to the packet and used by the routing tables toidentify the appropriate link(s) on which to route the packet. Thesource information is used by the destination node and any other nodeswhich are probed with the request to respond to the requestappropriately.

According to a specific embodiment and as mentioned above, theinterconnection controller in each cluster appears to the otherprocessors in its cluster as just another processor in the cluster.However, the portion of the shared memory space associated with theinterconnection controller actually encompasses the remainder of theglobally shared memory space, i.e., the memory associated with all otherclusters in the system. That is, from the perspective of the localprocessors in a particular cluster, the memory space associated with allof the other multi-processor clusters in the system are represented bythe interconnection controller(s) in their own cluster.

According to an even more specific embodiment which will be describedwith reference to FIG. 5, each cluster has five nodes (e.g., as shown inFIG. 2) which include four processors 202 a-d and an interconnectioncontroller 230, each of which is represented by a 3-bit node ID which isunique within the cluster. As mentioned above, each processor (i.e.,cluster node) may represent a number of sub-units including, forexample, CPUs, memory controllers, etc.

An illustration of an exemplary address mapping scheme designedaccording to the invention and assuming such a cluster configuration isshown in FIG. 5. In the illustrated example, it is also assumed that theglobal memory space is shared by 4 such clusters also referred to hereinas quads (in that each contains four local processors). As will beunderstood, the number of clusters and nodes within each cluster mayvary according to different embodiments.

To extend the address mapping function beyond a single cluster, eachcluster maps its local memory space, i.e., the portion of the globalmemory space associated with the processors in that cluster, into acontiguous region while the remaining portion of the global memory spaceabove and below this region is mapped to the local interconnectioncontroller(s). The interconnection controller in each cluster maintainstwo mapping tables: a global map and local map. The global map mapsoutgoing requests to remote clusters. The local map maps incomingrequests from remote clusters to a particular node within the localcluster.

Referring now to FIG. 5, each local cluster has a local memory map(501-504), which maps the local memory space (i.e., the contiguousportion of the global memory space associated with the local processors)into the respective nodes and maps all remote memory spaces (i.e., theremainder of the global memory space) into one or two map entriesassociated with the local interconnection controller(s), e.g., Node 4 ofQuad 3. Each node in the local cluster has a copy of the local map. Theinterconnection controller in each cluster also maintains a global map(505-508) relating these remote memory spaces with each of the otherclusters in the system. Each interconnection controller uses its copy ofthe local map (509-511) to map requests received from remote clusters tothe individual nodes in its cluster.

An exemplary transaction described with reference to FIG. 5 may beillustrative. In this example, Node 2 in Quad 3 generates a request thatmaps (via map 501) to the local interconnection controller (i.e., Node4). When the interconnection controller receives this request, itsglobal map 505 maps the address to Quad 2. The interconnectioncontroller then forwards the request to Quad 2. The interconnectioncontroller at Quad 2 uses its local memory map to determine the propernode to target for the request—Node 1 in this example.

In a particular implementation, each processor or cluster node islimited to eight memory map registers. The scheme described above withreference to FIG. 5 requires four entries for the local memory space andat most two registers for remote space. Therefore, according to morespecific embodiments, the two remaining entries can be used to subdivideregions. The eight mapping register limit requires that all memory localto a quad be allocated within a contiguous block. The interconnectioncontroller's local memory map in such embodiments is also eight entries.However, the size of the interconnection controller's global map size isdetermined by the number of clusters in the system. According to variousembodiments, the memory mapped I/O space is mapped by an identical setof mapping registers.

As described above, on the local cluster level, information from addressmapping tables is used to identify the appropriate link on which totransmit information to a destination node within the cluster. To effecttransmissions between clusters using the global mapping described above,a similar mechanism is needed. Therefore, according to variousembodiments, in addition to the local routing tables associated witheach node in a cluster, the interconnection controller maintains globalrouting information which maps the other clusters in the system to thevarious point-to-point transmission links interconnecting the clusters(e.g., links 111 of FIG. 1A).

According to a specific embodiment, two types of local routing tablesare employed: one for directed packets and one for broadcast packets.Each table (e.g., tables 406 of FIG. 4B) maintains a mapping betweentarget nodes and links. For directed packets, a separate table is usedfor request and for responses. This allows responses to be routed backto the requester along the same path as the request. Maintaining thesame route simplifies debugging and is not required for correctness. Forbroadcast packets, the corresponding table indicates on which links thebroadcast packet is forwarded. A broadcast packet may thus be routed tomultiple links.

In a particular implementation of the interconnection controller, itslocal tables map a local destination node to one of four links fordirected packets and any number of links for broadcast packets. Theinterconnection controller also maintains a global routing table whichmaps remote destination clusters to a particular remote link. Accordingto a particular embodiment, the interconnection controller also supportsmulticast of packets at the global routing level.

A specific embodiment of a routing mechanism will now be described withreference to FIGS. 6A and 6B. System 600 of FIG. 6A includes fourclusters each having a plurality of local nodes including nodes N₀ andN₁. The table of FIG. 6B combines all of the local and global routingtables of the system for illustrative purposes.

As part of an exemplary transaction, a CPU 602 at node N₀ in Cluster 0generates a packet directed to a CPU 604 at node N₀ in the Cluster 3.This packet could be, for example, a memory request that maps to amemory controller at that node. Because CPU 602 has no knowledge ofanything outside of its cluster, it generates the packet targeting nodeN₁ in Cluster 0 (i.e., the local interconnection controller 606) as thedestination. As discussed above, this is due to the fact that the localmemory map owned by node N₀ (see the relevant portion of the table ofFIG. 6B) identifies node N₁ as corresponding to all memory owned byremote clusters. Interconnection controller 606 receives the packet,uses its global address map (e.g., as described above) to determine thatthe final destination of the packet is Cluster 3, and generates a remotepacket targeting Cluster 3. Then, using its global routing table (i.e.,relevant portion of FIG. 6B), interconnection controller 606 determinesthat this packet must be sent out on link L₁. Similar to the localrouting mechanism described above, information identifying the sourceand destination cluster is appended to the packet.

When interconnection controller 608 at Cluster 1 receives the packet, italso determines that the packet is destined for Cluster 3 and determinesfrom its global routing table (FIG. 6B) that link L₂ must be used tosend the packet. Interconnection controller 610 at Cluster 3 receivesthe packet, determines that the packet is targeting the local cluster,and uses its local routing table (FIG. 6B) to determine that local linkL₀ must be used to send the packet to its destination. CPU 604 at nodeN₀ then receives the packet via link L₀. According to specificembodiments in which the node ID space is a 3-bit ID space, thismulti-level routing mechanism can be extended to eight local nodes withno specific limit on the number of clusters.

Embodiments described herein also address the issue of transactionidentification in a system having a plurality of multi-processorclusters. In general, the importance of the unique identification oftransactions in a multi-processor environment is understood. Where thetransaction identification or tag space is limited, mechanisms to extendit are needed to enable the interconnection of more than the maximumnumber of processors supported by the limited tag space. That is, in anenvironment with a plurality of clusters operating with identical localtransaction tag spaces, there is a potential for more than onetransaction to be generated in different clusters simultaneously withthe identical tag. Where those transactions occur between nodes indifferent clusters, the potential for conflict is obvious. Therefore,embodiments described herein provide mechanisms that extend the localtag spaces such that each transaction in the multi-cluster system isuniquely identified.

More specifically, these embodiments map transactions from the localtransaction tag space to a larger global transaction tag space. Asdescribed above, the local tag space is specified using the node ID, theunit ID, and a transaction ID. On top of that, the global tag space isspecified using a global cluster ID and a global transaction ID.According to one embodiment, the interconnection controllers in thesystem use their pending buffers to simplify the allocation andmanagement of the mapping and remapping actions. According to an evenmore specific embodiment and as will be described, additional protocolmanagement is used to maintain the uniqueness of the global transactiontags.

According to a specific embodiment, all transactions within a clusterare tagged with a unique ID generated by the requesting node. Theprocessors in each cluster that are not the interconnection controllersupport a 3-bit node ID, a 2-bit unit ID and a 5-bit transaction ID. Thecombination of these fields creates a 10 bit tag which is unique withinthe cluster. The unit ID represents sub-units within a node. It shouldbe noted that a particular node may or may not include a processor asone of its sub-units, e.g., the node might contain only memory.

According to one embodiment, to extend to the transaction tag spacebeyond the local cluster, each cluster's interconnection controller mapseach its cluster's local tag space into the global tag space using aQ-bit Cluster ID and a T-bit Transaction ID. In the exemplary system inwhich each cluster has a 5-bit transaction ID and there are fourclusters, T might be 7 and Q might be 2.

The local-to-global and global-to-local mapping techniques set forth inU.S. patent application Ser. No. 10/157,384 also may be used inconnection with the present invention. As noted above, that applicationis incorporated herein by reference for all purposes.

The previously-described methods and devices provide an exemplaryframework for intra-cluster and inter-cluster transactions. The presentinvention provides methods for injecting commands into a pipeline orqueue of intra-cluster or inter-cluster transactions, whether the queueis created according to the exemplary framework described above oraccording to another framework. As used herein, a “command” is usedbroadly and may include, for example, an instruction and associateddata, when appropriate. A “command” may include all or any part of atransaction, such as a request, a response, etc. According to preferredimplementations of the invention, commands may be injected into apipeline of transactions “on the fly,” i.e., while the system isrunning. Some preferred implementations do not require aninterconnection controller to be configured in a special mode in orderfor such transactions to be injected.

FIG. 7 is a flow chart that provides an overview of an exemplary methodof the present invention. Further details of this process will bedescribed below with reference to FIGS. 9 and 10. In step 705, an“inject command” indication is sent to a test interface. According tothe specific embodiment described with reference to FIG. 7, serviceprocessor 212 (see FIG. 2) sends the indication to TAP controller 321 ofinterconnection controller 230 (see FIGS. 3A and 3B). In otherembodiments, another device sends the indication and/or other signals toa test interface. The indication may be sent in response to a user'sinput, for example, during a troubleshooting and/or debugging operation.The user may also indicate the command to be inserted, whether byservice processor 212 or otherwise. In some embodiments, a userinteracts with a graphical user interface to send the indication and toinsert command.

In response to this command, in step 710 TAP controller 321 connects theTDI and TDO pins to a data register within test data block 315 that hasbeen designated a mailbox register. In step 715, service processor 212loads a command packet, associated data (if any) and status bits intothe mailbox register. An exemplary format for this information will bedescribed below with reference to FIG. 8.

The mailbox register that receives this information from the serviceprocessor is in a test clock domain that is typically a slower clockdomain than that of the interconnection controller. For example, the TAPclock domain may be on the order of 1 to 10 MHz, whereas the clockdomain of the interconnection controller may be on the order of 400 MHzor more. Therefore, in step 720, the fields in mailbox register of thetest clock domain are synchronized with the interconnection controllerclock domain and used to update the corresponding fields of a mailboxregister in the interconnection controller clock domain.

In step 725, the command from the mailbox register in theinterconnection controller clock domain is inserted into a commandbuffer of the interconnection controller. In step 730, status bits ofthe mailbox are updated to indicate that the command is no longerpending.

FIG. 8 illustrates an exemplary format 800 for packets to be shiftedinto mailbox registers. Preferably, the same format is used for themailbox registers of the test clock domain and of the interconnectioncontroller clock domain. In this example, the underlying protocol is theHT protocol and the mailbox register is used to facilitate the injectionof HT commands.

HT Data field 805 is used to encode data, if any, associated with acommand in the mailbox register. Data Valid field 810 includes a validbit for each double word of data in HT Data field 805. RCV LINK ID field815 states which link conveyed the packet to the mailbox. XMT LINK SELfield 820 indicates a link for transmission of the packet.

DATA PTRV field 825 is a “data pointer valid” field that indicateswhether there are data associated with a command in the mailbox. DATAPTR field 830 is the associated data pointer field. REM Link Ext field835 includes information (if relevant) pertaining to remote links. Forexample, such information may identify remote clusters, as describedabove with reference to FIGS. 5, 6A and 6B.

Next is the HT CMD field 840, which includes an HT command to beinjected via the mailbox. Such commands may allow, for example,configuration registers to be read or written, whether the configurationregisters are in a local cluster or a remote cluster. The command mayinitiate a new transaction in a local cluster (e.g., a Memory Readrequest to a local processor) or in a remote cluster (e.g., a Read Blockrequest to a remote cluster). Alternatively, the injected command may bea part of a transaction that is already in progress (e.g., a proberesponse to a Read request). Such commands may be particularly usefulduring a debugging operation for breaking deadlocks due to missingpackets, e.g., missing probe responses from a remote cluster. As notedabove, the present invention is not limited to injecting HT commands,but may be used with any suitable protocol.

SPJTAG_CMD field 845 is for commands directed to the SPJTAG moduleinside the Special Functions Unit illustrated in FIG. 10. According tosome implementations, SPJTAG_CMD field 845 is relatively small, e.g., 3bits. If SPJTAG_CMD field 845 includes a non-zero value, HT CMD field840 will be ignored.

According to one implementation, there are 2 SPJTAG commands. The firstSPJTAG command clears the Finished and Pending bits. This command isused when 2 responses are expected for an injected HT command. After thefirst response is captured and shifted out, this SPJTAG command isshifted in so that the F and P bits get cleared. This procedure allowsthe second response from the system to be written into the mailbox. Thesecond response can then be shifted out during the next Capture-DR.

The second SPJTAG command resets the Configuration register Accessmechanism inside interconnection controller 230. This command is used insituations where the configuration register access mechanism insideHorus fails to operate correctly and needs to be reset.

Fields 850 through 870 are single-bit fields according to someimplementations. When NRE bit 850 is set, this indicates that noresponse is to be expected for the command shifted in. Accordingly,Finished bit 870 will be set as soon as the command is accepted. WhenFRC bit 855 is set, the command is forced into the system and Finishedbit 870 is ignored. PRIO bit 860 indicates that the command should besent directly to Special Functions Configuration Access Dispatch(“SPCAD”) unit 1015, (see FIG. 10). PRIO bit 860 is used with commandsto access configuration registers in the local interconnectioncontroller 230. When PRIO bit 860 is not set, the injected HT command issent to SPE Protocol Engine 1010 for decoding. If the command is aconfiguration access command to the local interconnection controller,SPE Protocol Engine 1010 forwards the command to SPCAD unit 1015, whichsends a response to SPE Protocol Engine 1010. SPE Protocol Engine 1010then forwards the response back to SPJTAG unit 1038, where the responseis written into the mailbox register.

If the PRIO bit is set, however, the injected configuration accesscommand is sent directly to SPCAD unit 1015, bypassing the SPE ProtocolEngine 1010. In addition, the response from SPCAD unit 1015 is sentdirectly back to SPJTAG unit 1038, bypassing SPE Protocol Engine 1010.

Thus, the PRIO bit mechanism provides a way of bypassing SPE ProtocolEngine 1010 for configuration accesses to the local interconnectioncontroller. The PRIO bit mechanism offers 2 benefits. First, it providesa way to work around logic bugs in the logically complex SPE ProtocolEngine 1010 (that may make SPE Protocol Engine 1010 inoperable) bybypassing SPE Protocol Engine 1010. Second, the PRIO bit mechanismprovides a less intrusive access to the local interconnection controllerconfiguration registers, in that the injected commands do not contendwith transactions that exist in the command pipeline controlled by SPEProtocol Engine 1010. PRIO bit 860 is set, for example, forconfiguration Read/Write commands to the local interconnectioncontroller.

Pending bit 865 indicates that a new command has been shifted into themailbox register. Finished bit 870 is set when the command has beencompleted and indicates that a response to the command is ready to becaptured from the mailbox register.

FIG. 9 illustrates some aspects of injecting commands according to thepresent invention. As noted above, after an instruction register of TAPcontroller 321 receives an instruction (e.g., from service processor212) to initiate the process of injecting a command, TAP controller 321connects TDI pin 905 and TDO pin 910 to mailbox register 915. Mailboxregister 915 is in the test clock domain (here, the TAP domain). Mailboxregister 915 and corresponding mailbox register 920 in theinterconnection controller clock domain may have the format 800described above, but in FIG. 9 only selected fields are shown.

After the mailbox register 915 is connected with TDI 905 and TDO 910, aTAP controller 321 enters the Shift DR state (see FIG. 3C). In thisstate, a packet including a command, associated data (if any) and statusbits is then loaded into mailbox register 915 via TDI 905. In someembodiments, the packet is loaded into mailbox register 915 by serviceprocessor 212. In other embodiments, such information is loaded intomailbox register 915 via another device configured to access testinterface 313. As noted above, the packet may be loaded into mailboxregister 915 under the control of a user, possibly by interacting with agraphical user interface.

According to one specific embodiment, in order for a successful updateto occur, a command must be loaded with Pending bit 865 set and Finishedbit 870 clear. Moreover, in this example, a sample of the status flagsobtained from Capture-DR state 342 must show that a prior command wasaccepted (Pprev=0) and completed (Fprev=1). After TAP controller 321determines that Pending bit 865 is set and Finished bit 870 is clear,TAP controller 321 enters the Update DR state (see FIG. 3C) and assertsan Update DR signal to mailbox register 915. Upon receiving the UpdateDR signal, mailbox register 915 determines that the entire packet hasbeen shifted in and that mailbox register 915 may perform an update.Accordingly, the command, data and status fields of correspondingmailbox register 920 in the interconnection controller clock domain arethen updated.

If FRC bit 855 is set, then the Update is “forced” and the Fprev statusbit is ignored. FRC bit 855 is used, for example, if Finished bit 870 isnot asserted even after the interconnection controller has completed theprevious command, or if the previous command does not have an expectedresponse.

Because the update occurs in the test clock domain, the update signalmust be synchronized to the interconnection controller's clock domain.According to some embodiments, Special Functions Unit (SPFU) 1005 (seeFIG. 10) performs this synchronization. The synchronized update isqualified with the previously-mentioned conditions regarding the commandand status fields.

After the command, data and status fields of mailbox register 920 havebeen loaded, the packet or packets are forwarded to SPFU 1005 of theinterconnection controller. (In alternative embodiments, mailboxregister 920 is part of SPFU 1005.) SPFU 1005 inserts the command packetinto command pipeline 1006 from buffer 1007. Preferably, SPFU 1005inserts the command into command FIFO 1008 which may be located, forexample, at the input of Special Protocol Engine (SPE) 1010. SPFU 1005inserts data packets into data stream 1009. Transmitter 1020 forwardsthe data and commands to the appropriate destinations.

If the injected command needs to access the local configurationregisters, then the SPE 1010 will later send the command back to SPCAD1015. However, if PRIO bit 860 is set, the packet is send directly toSPCAD 1015 directly, bypassing SPE 1010. After SPFU 1005 accepts thecommand, SPFU 1005 changes Pending bit 865 in mailbox register 920 to“0,” indicating that the command has been processed.

According to some embodiments, SPE 1010 has other functions. Forexample, at the time the system comes out of “reset” mode, the local andremote protocol engines are not functioning right away. The onlyfunctioning protocol engine at that time is SPE 1010, which programs andconfigures the system. Once the system is configured, other protocolengines are activated and take over many system transactions, but SPE1010 is still responsible for special instructions such as broadcasts,interrupts, etc.

Preferably, the packets are assigned an identifier (e.g., a node ID)that is associated with mailbox register 920. The identifier indicatesthat the command or data originated from the mailbox and allows, forexample, a response to an inserted command to be directed back to themailbox according to the intra-cluster and inter-cluster protocols.

In this embodiment, service processor 212 polls the data, command andstatus bits of the mailbox register during Capture-DR state 342, thenshifts the results out TDO pin 910 for inspection. Preferably, onlyPending bit 865 and Finished bit 870 are shifted out for inspection. Ifthe captured state of Pending bit 865 is clear, service processor 212knows that the command previously shifted in has been accepted.

After SPE 1010 receives the injected command, SPE 1010 sends the commandthrough the pipeline according to the normal intra-cluster protocol. Ifthe command triggers a response, the response will come back to SPE1010. According to some implementations, when SPE 1010 receives theresponse, SPE 1010 (or another component of SPFU 1005) will cause theresponse to be written into CMD/RESP field 950 of mailbox register 920,e.g., by asserting an SP response write enable (“SPRespWrE”) command.SPFU 1005 will cause associated data, if any, to be written into datafield 960, e.g., by asserting an SP data write enable (“SPDataWrE”)command. Because the data and response may or may not be synchronized,it is preferable to have separate commands for controlling this process.Finished bit 870 is set only after both the data and response arewritten into mailbox 920.

Meanwhile, service processor 212 has continued to poll the contents ofthe mailbox register (or, at least, Finished bit 870 is shifted out forinspection). Preferably, while the data, command and status bits arebeing shifted out, a new set of data, command and status bits are beingshifted in. If the captured state of the Finished bit 870 is clear,service processor 212 knows that the command previously shifted in hasnot been completed. Accordingly, if the command shifted in has not beencompleted, the contents of mailbox 915 are overwritten with the contentsof mailbox 920.

If the captured state of the Finished bit 870 is set, service processor212 knows that the command previously shifted in has been completed andthat a response packet can be copied into the test clock domain inCapture-DR state 342. After capture, the entire contents of mailbox 915are shifted out. Service processor 212 would then continue polling andinjecting new transactions. In preferred implementations, serviceprocessor 212 does not need to change the TAP instruction betweensubsequent commands.

While the invention has been particularly shown and described withreference to specific embodiments thereof, it will be understood bythose skilled in the art that changes in the form and details of thedisclosed embodiments may be made without departing from the spirit orscope of the invention. For example, specific embodiments have beendescribed herein with reference to a particular multi-processorarchitecture having a limited node ID space and flat request mappingfunctions. It will be understood, however, that the present inventionapplies more generally to a wide variety of multi-processorarchitectures that employ a point-to-point communication infrastructureto facilitate communication among the various nodes in the system. Inaddition, each of the various aspects of the embodiments describedherein relating to, for example, address mapping, routing mechanisms,and transaction identification, may be used in combination with variousalternatives of other ones of these aspects without departing from thescope of the invention.

It should also be understood that the various embodiments of theinvention may be implemented or represented in a wide variety of wayswithout departing from the scope of the invention. That is, for example,the interconnection controller described herein may be represented(without limitation) in software (object code or machine code), invarying stages of compilation, as one or more netlists, in a simulationlanguage, in a hardware description language, by a set of semiconductorprocessing masks, and as partially or completely realized semiconductordevices. The various alternatives for each of the foregoing asunderstood by those of skill in the art are also within the scope of theinvention. For example, the various types of computer-readable media,software languages (e.g., Verilog, VHDL), simulatable representations(e.g., SPICE netlist), semiconductor processes (e.g., CMOS), and devicetypes (e.g., ASICs) suitable for designing and manufacturing theprocesses and circuits described herein are within the scope of theinvention. Moreover, a test interface of a processor may be used forreceiving injected commands in a manner parallel to that describedherein for an interconnection controller.

Finally, although various advantages, aspects, and objects of thepresent invention have been discussed herein with reference to variousembodiments, it will be understood that the scope of the inventionshould not be limited by reference to such advantages, aspects, andobjects. Rather, the scope of the invention should be determined withreference to the appended claims.

1. A computer system comprising a plurality of processor clusters, eachcluster including a plurality of nodes, the nodes including processorsand an interconnection controller interconnected by point-to-pointintra-cluster links, each of the processors and the interconnectioncontroller communicating within a cluster via an intra-clustertransaction protocol, inter-cluster links being formed betweeninterconnection controllers of different clusters, each of theprocessors and the interconnection controller in a cluster having a testinterface for communicating with service processor, at least one of thenodes in a cluster is a command-injecting node configured to receive acommand via a test interface and to inject the command into a queue ofcommands according to the intra-cluster transaction protocol.
 2. Thecomputer system of claim 1, wherein the test interface is compliant withthe Joint Test Action Group standard.
 3. The computer system of claim 1,wherein the injected command is selected from the group consisting of(a) a command for reading a configuration of a node within a localcluster that includes the service processor that made the injectedtransaction; (b) a command for writing a configuration of a node withina local cluster that includes the service processor that made theinjected transaction; (c) a command for reading a configuration of anode within a remote cluster that does not include the service processorthat made the injected transaction; and (d) a command for writing aconfiguration of a node within a remote cluster that does not includethe service processor that made the injected transaction.
 4. Thecomputer system of claim 1, wherein the injected command comprises a newtransaction.
 5. The computer system of claim 1, wherein the injectedcommand comprises a part of a transaction that was in progress beforethe command was injected.
 6. The computer system of claim 1, wherein theinterconnection controllers communicate between clusters via aninter-cluster transaction protocol.
 7. The computer system of claim 1,wherein the test interface further comprises a mailbox register forreceiving the command.
 8. The computer system of claim 1, wherein acommand is received from the test interface in a first clock domain andat least part of the command-injecting node operates in a second clockdomain, and wherein the command-injecting node is further configuredfor: receiving injected transactions in the first clock domain; andsynchronizing the injected transactions to the second clock domain. 9.The computer system of claim 1, wherein the command-injecting node is aninterconnection controller.
 10. The computer system of claim 1, whereinthe command-injecting node is any device capable of driving the JTAGport.
 11. The computer system of claim 4, wherein the new transaction iswithin a local cluster that includes the command-injecting node.
 12. Thecomputer system of claim 4, wherein the new transaction is within aremote cluster that includes the command-injecting node.
 13. Thecomputer system of claim 7, wherein the mailbox register is configuredto be connected with a test data in interface and a test data outinterface.
 14. An interconnection controller for use in a computersystem comprising a plurality of processor clusters, each clusterincluding a plurality of nodes, the nodes including processors and aninstance of the interconnection controller interconnected bypoint-to-point intra-cluster links, each of the processors and theinterconnection controller within a cluster communicating via anintra-cluster transaction protocol, the interconnection controllerconfigured to receive commands via a test interface and to inject thecommands into a queue of pending commands according to the intra-clustertransaction protocol.
 15. The interconnection controller of claim 14,wherein a service processor in a cluster that includes theinterconnection controller operates in a first clock domain, wherein theinterconnection controller operates in a second clock domain, andwherein the interconnection controller is further configured for:receiving injected transactions from the service processor in the firstclock domain; and synchronizing the injected transactions to the secondclock domain.
 16. The interconnection controller of claim 14, furthercomprising a mailbox register for receiving the injected transactionfrom the service processor.
 17. An integrated circuit comprising theinterconnection controller of claim
 14. 18. At least onecomputer-readable medium having data structures stored thereinrepresentative of the interconnection controller of claim
 14. 19. A setof semiconductor processing masks representative of at least a portionof the interconnection controller of claim
 14. 20. The integratedcircuit of claim 17, wherein the integrated circuit comprises anapplication-specific integrated circuit.
 21. The at least onecomputer-readable medium of claim 18, wherein the data structurescomprise a simulatable representation of the interconnection controller.22. The at least one computer-readable medium of claim 18, wherein thedata structures comprise a code description of the interconnectioncontroller.
 23. The at least one computer-readable medium of claim 21,wherein the simulatable representation comprises a netlist.
 24. The atleast one computer-readable medium of claim 22, wherein the codedescription corresponds to a hardware description language.
 25. Theinterconnection controller of claim 14, wherein the queue of pendingcommands is controlled by a protocol engine, the interconnectioncontroller further configured to process access commands for accessingconfiguration registers of the interconnection controller withoutforwarding the access commands to the protocol engine.
 26. Theinterconnection controller of claim 25, further comprising aconfiguration access unit for processing access commands.